System and method for aggregate data from multiple sources to provide a single cim object

ABSTRACT

Method and system for aggregating data regarding a system component from multiple data sources to provide a single aggregated Common Information Model (“CIM”) object are described. In one embodiment, the method comprises requesting data regarding a system component from a first one of the data sources; upon receipt of the requested system component data from the first one of the data sources, updating an aggregate CIM object for the system component using the received system component data in accordance with a priority of the first one of the data sources relative to the remaining data sources; and repeating the requesting and updating in connection with each of the remaining data sources in accordance with a relative priority of the remaining data source.

RELATED APPLICATION DATA

This application is a continuation of U.S. patent application Ser. No. 11/376,907, filed Mar. 16, 2006, now allowed, which is incorporated by reference herein for all purposes.

BACKGROUND

Common Information Model (“CIM”) is a standard set forth by the Distributed Management Task Force (“DMTF”) that allows for a common model of providing information regardless of hardware or operating system (“OS”) platform. CIM provides a common definition of management information for systems, networks, applications and services and allows for vendor extensions thereto. CIM is a vendor-agnostic industry management standard. A CIM object manager (“CIMOM”) is essentially a server for servicing CIM requestsA Common Information Model (“CIM”) provider provides on a CIM platform data representing a single entity. In the case of hardware, there will theoretically be an instance of a CIM object representing each component, including, for example, each processor, video card, etc. Hardware data is derived from multiple sources, including, but not limited to, Intelligent Platform Management Interface (“IPMI”), Hardware Abstraction Layer (“HAL”), System Management BIOS (“SMBIOS”), sysfs, and proprietary third party sources. Each of these sources has its own interface, some of which are very complex. There could be a representation of each component in only one, many, or all of the available data sources.

CIM promises a single interface to obtain the information about such components; however, the CIM provider requires a component profile provider to aggregate all of the data sources into a single CIM instance. This would traditionally require that for each component entity type (CIM provider), a profile provider would have to know how to interface with each of the data sources and aggregate that data into a single object.

SUMMARY

In response to these and other problems, in one embodiment, a method is provided for aggregating data regarding a system component from multiple data sources to provide a single aggregated Common Information Model (“CIM”) object. The method comprises requesting data regarding a system component from a first one of the data sources; upon receipt of the requested system component data from the first one of the data sources, updating an aggregate CIM object for the system component using the received system component data in accordance with a priority of the first one of the data sources relative to the remaining data sources; and repeating the requesting and updating in connection with each of the remaining data sources in accordance with a relative priority of the remaining data source.

In another embodiment, the system comprises, for each of the data sources, means associated with the data source for responding to a request for a CIM object for a system component; and an aggregation module connected to each of the means for responding; wherein responsive to a request from a client application for a CIM object for a particular system component, the aggregation module receives a CIM object for the particular system component from each of the data sources and combines the received CIM objects into a single aggregated CIM object for the particular system component.

In still another embodiment, the system comprises means for requesting data regarding a system component from a first one of the data sources; and means responsive to receipt of the requested system component data from the first one of the data sources for updating an aggregate CIM object for the system component using the received system component data in accordance with a priority of the first one of the data sources relative to the remaining data sources; wherein the requesting and updating are repeated in connection with each of the remaining data sources in accordance with a relative priority of the remaining data source.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a system for aggregating data from multiple objects regarding a system component to provide a single CIM object to a client application.

FIG. 2 is a flow diagram of the system of FIG. 1 in accordance with one embodiment.

FIG. 3 illustrates an embodiment of a method for aggregating data from multiple objects regarding a system component to provide a single CIM object to a client application.

DETAILED DESCRIPTION OF THE EMBODIMENTS

This disclosure relates generally to CIM objects and, more specifically, to a system and method for aggregating data from multiple CIM objects regarding a system component to provide a single aggregated CIM object to a client application. It is understood, however, that the following disclosure provides many different embodiments or examples. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.

Referring to FIG. 1, in one embodiment, a system 10 enables aggregation of data concerning a single system component from multiple data sources for the purpose of providing a single aggregated CIM object to a client application. As illustrated in FIG. 1, the system 10 includes one or more data sources, represented in FIG. 1 by data sources 12 a-12 c, each of which comprise a native data source interface for a different provider. For example, the data source 12 a comprises a native data source interface for IPMI, the data source 12 b comprises a native data source interface for SMBIOS, and the data source 12 c comprises a native data source interface for a third party designated “proc”. It will be recognized that, for each type of system component, a common model of possible data about that component is derived; this is referred to as the common CIM schema. Each of the data sources 12 a, 12 b, 12 c, stores data for each of a number of system components. It will be recognized that the information included in each of the interfaces for a particular hardware element will be dependent on the corresponding source.

For each of the data sources 12 a-12 c, a separate CIM provider, comprising a CIMOM plug-in module, is provided for publishing the data it knows about the various types of system components into its own CIM namespace. In particular, one or more IPMI providers, represented in FIG. 1 by an IPMI provider 14 a, publishes all of the data it knows about all system components from IPMI into appropriate component objects in an IPMI namespace 16 a. Similarly, one or more SMBIOS providers, represented in FIG. 1 by an SMBIOS provider 14 b, publishes all of the data it knows about all system components from SMBIOS into appropriate component objects in an SMBIOS namespace 16 b and a proc provider 14 c publishes all of the proprietary data it possesses about all system components into appropriate component objects in a proc namespace 16 c. It will be recognized that, although only three providers are illustrated in FIG. 1, there may be more or fewer providers in alternative embodiments.

A composite data provider 18 includes an aggregation module 20, the function of which is to provide awareness of all of the namespaces 16 a-16 c and to aggregate information from those namespaces. The aggregation module 20 uses configuration settings, which may be specified in a configuration file 21, to know which namespaces to aggregate, as well as for configuration settings for precedence rules, such as which namespace is deemed more accurate than others if there is conflicting data. Additionally, the aggregation module 20 uses “deviceIDs” that contain both an entity type and an instance number to identify which devices from each namespace are common and should be aggregated. Finally, the aggregation module 20 publishes one common instance for each instance that exists in at least one of the namespaces 16 a-16 c. This single instance provides all known information with regard to a single system component without regard to the origin of that information.

In operation, and as more fully described below, a client application 22 makes a request to a System Management Architecture for Server Hardware (“SMASH”) namespace 24 for data regarding a system component. In accordance with features of one embodiment, the response from the SMASH namespace 24 to this request comprises an aggregated CIM object.

Referring now to FIG. 2, operation of the system 10 in accordance with one embodiment in response to a request from a client application will be described. The process is initiated with a request 40 from the client 22 to the SMASH namespace 24 for data regarding a system component designated “CPU1”. The SMASH namespace 24 submits a corresponding request 42 to the aggregation module 20 of the composite device provider 18, which in turn queries the namespaces 16 a, 16 b, 16 c, via requests 44 a, 44 b, and 44 c, respectively. Each of the namespaces 16 a, 16 b, 16 c, queries its respective data sources 12 a, 12 b, 12 c, via the respective provider 14 a, 14 b, 14 c, as represented by arrows 46 a, 46 b, 46 c, and 48 a, 48 b, 48 c. In response to the query from the respective namespace 16 a, 16 b, 16 c, each of the data sources 12 a, 12 b, 12 c, provides data stored therein regarding the specified hardware element, e.g., CPU1, as represented by arrows 50 a, 50 b, 50 c, and 52 a, 52 b, 52 c. The namespaces 16 a, 16 b, 16 c, return this data to the aggregation module 20, as represented by arrows 54 a, 54 b, 54 c.

The data returned to the aggregation module 20 from each of the namespaces 16 a, 16 b, 16 c, comprises a CIM object. Each of the CIM objects is populated differently, depending on the data source from which it was derived. In one embodiment, as will be described in detail below, the aggregation module 20 aggregates the CIM objects received from the namespaces 16 a, 16 b, 16 c, in a manner specified by the configuration file 21, which indicates, among other things, an order of precedence among the data sources 12 a, 12 b, 12 c. The aggregated CIM object is returned to the SMASH namespace 24, as represented by an arrow 56. The SMASH namespace 24 provides the aggregated CIM object to the client application 22, as represented by an arrow 58.

FIG. 3 is a flowchart illustrating a method aggregating data from multiple objects regarding a single component to provide an aggregated CIM object to a client application. As shown in FIG. 3, in step 60, a list of aggregate data sources, sorted in reverse order of priority, is obtained. Using the system 10 shown in FIGS. 1 and 2 as an example, the list of data sources would include the IPMI data source 12 a, the SMBIOS data source 12 b, and the proc data source 12 c. For the sake of example, it will be assumed that the configuration file 21 specifies that the IPMI data source 12 a is the highest priority, the SMBIOS data source 12 b is the second highest priority, and the proc data source 12 c is the lowest priority among the data sources; therefore, the proc data source would be listed first, the SMBIOS data source would be listed second, and the IPMI data source would be listed last. In step 62, beginning with the first listed data source, the CIM object for the component of interest is requested from the data source. The process of requesting and obtaining the specified object from the data source is detailed above with reference to FIG. 2. Using the example illustrated in FIG. 2 and the order of priority specified above, the result of step 62 would be that a CPU1 object is requested from the proc data source 12 a.

In step 64, a determination is made whether the requested object exists in the data source; that is, whether the object has been returned from the data source. If so, in step 66, all data from the returned object is copied into an aggregated object for the component of interest. In performing step 66, any existing data in the aggregated object is overwritten with data included in the returned object. As previously noted, the data sources are processed in reverse order of priority, thus ensuring that the data provided by the data source with the highest order of priority is included in the aggregated object. If a negative determination is made in step 64, execution proceeds directly to step 68. In step 68, a determination is made whether there are more data sources in the list of data sources from which to request CIM objects. If so, in step 70, the CIM object for the component of interest is requested from next data source and steps 64-70 are repeated for each of the remaining data sources. If a negative determination is made in step 68, execution proceeds to step 72. In step 72, the aggregation is complete and the aggregated object is returned to the client application, as described with reference to FIG. 2.

It will be recognized that, as opposed to being sorted in reverse order of priority, the list of aggregate data sources obtained in step 60 may be sorted in order of priority, in which case, in step 66, the only data that will be copied from the returned object into the aggregated object will be data that does not already exist in the aggregated object.

While the preceding description shows and describes one or more embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present disclosure. For example, various steps of the described methods may be executed in a different order or executed sequentially, combined, further divided, replaced with alternate steps, or removed entirely. In addition, various functions illustrated in the methods or described elsewhere in the disclosure may be combined to provide additional and/or alternate functions. Therefore, the claims should be interpreted in a broad manner, consistent with the present disclosure. 

What is claimed is:
 1. A Common Information Model object manager (“CIMOM”) for aggregating multiple Common Information Model (“CIM”) objects for a system component from different data sources into a single aggregated CIM object, the CIMOM comprising: for each of the data sources, means associated with the data source for responding to a request for a CIM object for a system component; and an aggregation module connected to each of the means for responding, the aggregation module thereby updating a single aggregate CIM object for the system component using the received system component data; wherein responsive to a request from a client application for a CIM object for a particular system component, the aggregation module receives a CIM object for the particular system component from each of the data sources and repeatedly combines the received CIM objects into the single aggregated CIM object for the particular system component.
 2. The CIMOM of claim 1 further comprising a configuration file indicating a relative priority of the received CIM objects.
 3. The CIMOM of claim 2 wherein the aggregation module combines the received CIM objects by copying the received CIM objects to the aggregated CIM object in sequential order from lowest to highest priority thereof as indicated in the configuration file, wherein the copying comprises, for each received CIM object, overwriting any existing data in the aggregate system component CIM object that conflicts with a portion of the received CIM object with the received CIM object portion.
 4. The CIMOM of claim 2 wherein the aggregation module combines the received CIM objects by copying the received CIM objects to the aggregated CIM object in sequential order from highest to lowest priority thereof as indicated in the configuration file, wherein the copying comprises writing to the aggregate CIM object only a portion of the received CIM object that is not already included in the aggregate CIM object.
 5. The CIMOM of claim 1 wherein the aggregation module is associated with a CIM Object Manager (“CIMOM”) plugin module.
 6. The system of claim 1 wherein each of the means for responding comprises a CIM Object Manager (“CIMOM”) plug in module and a CIMOM namespace.
 7. The CIMOM of claim 1 further comprising a CIM Object Manager (“CIMOM”) namespace for receiving the request from the client application and forwarding the request to the aggregation module and for returning the aggregated CIM object to the client application.
 8. The CIMOM of claim 1 wherein at least one of the multiple data sources is a data source selected from the group consisting of Intelligent Platform Management Interface (“IPMI”), Hardware Abstraction Language (“HAL”), System Management BIOS (“SMBIOS”), and sysfs.
 9. The CIMOM of claim 1 wherein at least one of the multiple data sources is a proprietary third party provider. 